Empirical study of analysts' practices in packaged software implementation at small software enterprises

This study investigates the practices of Requirements Engineering (RE) for packaged software implementation, as enacted by Small Packaged Software Vendors (SPSVs). Throughout the study, a focus on the actions carried out by SPSV analysts during RE is maintained, rather than a focus on the actions of client companies. The study confirms assertions in the literature, finding that most contemporary RE practices are unsuitable for SPSVs. The research investigated the means by which SPSVs can adopt, follow and adapt the best possible RE practices for Packaged Software Implementation (PSI), an explanation of the collection of qualitative and quantitative data during an case study in packaged software vendors. The research findings lead to introduced new methods of documentation, was not as concerned as general RE practice with looking for domain constraints or with collecting requirements and viewpoints from multiple sources, was more likely to involve live software demonstrations and screenshots to validate user needs, and was more likely to involve the compilation of a user manual. In PSI, prioritising requirements is not a basic practice; instead, analysts collect requirements in a circular process, with managers then directing analysts regarding which requirements to direct most attention toward. PSI was also found to place emphasis on assessing requirements risks and on considering the relationship between users’ needs and the interrelationships between software functions, as analysts engaging in PSI do not wish to disrupt functions of their software when making modifications in response to client requests.